Hi All, We have an office of about 30 people which are spread over 6-7 different websites/business all running under one company group. We are using exchange 2003 to manage all ourusersemail, we have multiple domains installed and everything is 'working' fine. Our email is all routed via our ISP's SMTP connection which leads to three problems: 1) Our reverse DNS nevermatches, we could request this to be updated but it would only ever match for one of the domains in our business 2) Our reputation is spread across multiple domains/businesses, I might like to manage the reputation of each domain seperatly 3) We arereliant on our ISP keeping a clean reputation I would like to route mail through different relay's so for example something@corp.domain -> use relay X -> which reverse DNS matches something@domain -> use relay Y-> which reverse DNS matches something@domain2-> use standard connection -> via ISP We can find plenty of support on adding multiple incoming SMTP connections but not outgoing filters. Any help/links to resources would beappreciated.

On Mon, 9-Nov-09 10:43:21 GMT, Andy_Slack wrote:iple domains/businesses, I might like to manage the reputation of each domain seperatly 3) We are reliant on our ISP keeping a clean reputation I would like to route mail through different relay's so for example something@corp.domain -> use relay X -> which reverse DNS matches something@domain -> use relay Y -> which reverse DNS matches something@domain2 -> use standard connection -> via ISP We can find plenty of support on adding multiple incoming SMTPconnections>but not outgoing filters. Any help/links to resources would be appreciated. I think you're asking about routing outbound email based on thesender's domain. There's nothing that I know of in Exchange that willdo that.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

I think you're asking about routing outbound email based on thesender's domain. There's nothing that I know of in Exchange that willdo that. Yes you are 100% correct, this is what we are trying to do, thanks for clarifying in the correct way. If anybody can help it would be very muchappreciated.

Hi,Exchange itself doens't have this feature. Maybe the customization transport agent canworkaround this issue. You need to post the questionon the Development forum.http://social.technet.microsoft.com/Forums/en/exchangesvrdevelopment/threadsThanksAllen

Hi Lets assume you have user@corp.domain and user@domain.@corp.domain and @domain is are in different active directory sites and each AD site has its own hub transport serverthen its possible to route outbound email based on the sender's domain.Let me know if the above scenario true in your case.Azm.

I think you're asking about routing outbound email based on thesender's domain. There's nothing that I know of in Exchange that willdo that. Yes you are 100% correct, this is what we are trying to do, thanks for clarifying in the correct way. If anybody can help it would be very muchappreciated. Hi All, I just have (I think) the same problem. In my case however, I have an orgnization where there are 2 domains hosted in our exchange servers. Our users have to have the ability to send-as a username in either one of the domains as we have two distinct business units, but the users may do work for one or the other.Well, our ISP has set the RDNS entries for ONE of the domains, when users send from an account of the other domain, we experience (some times) bounce backs. Some destinations are famous... like comcast. Well, we only have one static IP for this SMTP server, therefore only one RDNS resolution. I cannot return both domains.or can I? this seems to me should be such acommon situation that I'm inclined to believe that comcast is just wrong trying to match the domain names. I think they should stop by verifying that we're not an open relay and than an RDNS exist. Any domain maching will lead inmediately to invalid bounces.If anyone in the forum can shed some light on how this should be configured please let me know. Any help will be greately appreciated.I have had some success with certain ISPs by contacting them and they have flagged our domain(s) and server.No luck with comcast. we seem to be kind of uninportant for them.Thank you allmrbello